Controller Connection

Before you can configure and upload to the Controllers they must be connected to the PC running the Designer software. Depending on the Controller, this connection can generally be made in one of two ways:

Ethernet

This is the most flexible method of connecting one or more Controllers and is well suited to a permanent installation. TCP/IP Ethernet itself needs configuration and management, in particular the setting of IP addresses.

If a controller is on an incompatible network, it will be displayed in the Network Mode with Grey text.

DHCP (default)

Pharos Controllers are factory set to receive an IP address from a DHCP server so one must be present on the network.

Link local (DHCP error)

Should the Controller fail to find a DHCP server it will assign itself a "link local" (169.254.x.x) IP address which can be used with Designer to establish a temporary connection. However, a DHCP server should be found or a Static IP address set to establish a permanent connection.

Static IP (optional)

It is sometimes desirable to set a Static IP address so that the IP address of the Controller is always known (DHCP served IP addresses can change). Refer to Controller configuration.

Multicast

Pharos Controllers and Remote Devices also use a block of Multicast addresses for "discovery" and Remote Device communication so these addresses must be available: 239.192.38.7 and 239.192.38.8

Default gateway

Must be consistently set to either nothing or a valid IP address.

Managed switches and firewalls

Managed Ethernet switches and your PC's Security Firewall can conspire to make life difficult - by blocking Multicast addresses for example. Pharos recommends the use of Unmanaged switches and disabling your PC's Firewall if you're experiencing connection problems.

eDMX considerations

While the LPC X has a second, dedicated Ethernet Protocol port with its own IP settings, the TPC and LPC 1, 2 & 4 must share their single Ethernet port. However, this single Ethernet port can be configured with two IP addresses, making it easier to manage routing of output protocol data. See Controller Protocols.

For further information about the Controller hardware and its input/output ports please refer to the Installation Guide supplied with the unit or available from the website.

Ethernet over USB

In addition to being able to connect to a controller using a traditional Ethernet connection, Designer is able to communicate with an LPC using an Ethernet over USB connection. The controller will appear in Designer as if the connection has been made using Ethernet (with the controller having an IP address) and all the same functionality is available, but the physical connection is made using a USB cable.

Network window

Once you have connected the Controller, select the Network tab to view your connected Controllers & Remote Devices:

If a controller is on a different network, and is not discovered on USB, it will appear as grey in the network spreadsheet. If a controller is on a different network (regardless of discovery on USB), a warning message is shown in the Controller Config tab.

Controller firmware

IMPORTANT: Controllers must be running the same version of firmware The embedded operating system, stored in internal flash memory or on the memory card. as the Designer software. Controllers with incompatible firmware will be highlighted in red.

NOTE: Controller's on a v1.x.x firmware version will not show up in Designer 2. See Conversion for more details.

To update a Controller's firmware:

Select the incompatible Controller, the row will be highlighted
Press Reload Firmware on the network toolbar
The firmware update will proceed - you must not disturb this process

Alternatively a utility application is provided that also allows you to update the LPC X's bootloader Bootstrap loader; a small software program, stored in internal flash memory, that is responsible for loading the firmware or operating system. and firmware, see LPC X Recovery Tool. There is a recovery procedure for the TPC and LPC 1/2/4.

The EXT's firmware is updated directly from the TPC. If the TPC detects that a connected EXT has the wrong firmware version then it will automatically update it - you must not disturb this process. The EXT's 'TPC Active' LED will illuminate continuously when this process has completed successfully.

Once all the connected Controllers have compatible firmware you can associate them with project Controllers and configure their hardware.